Capturing Design Rationale in Concurrent Engineering Teams1

نویسنده

  • Mark Klein
چکیده

When an artifact is designed nowadays the typical output of this activity includes blueprints, CAD files, manufacturing plans and other documents describing the final result of a long series of deliberations and tradeoffs by the participants of concurrent engineering (CE) teams. The underlying intent and logical support (i.e.therationale ) for the decisions captured therein is usually lost, or is represented at best as a scattered collection of paper documents, project and personal notebook entries as well as the recollections of the artifact’s designers. This design rationale information can be very difficult to access by human agents and is represented such that computers can provide little support for managing and utilizing it.

برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید

ثبت نام

اگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید

منابع مشابه

Capturing Geometry Rationale for Collaborative Design1

When an artifact is designed the typical output consists of documents describing the final result of a long series of deliberations and tradeoffs by the participants of collaborative design (AKA concurrent engineering) teams. The underlying intent and logical support (i.e.the rationale) for the decisions captured therein is usually lost, or is represented at best as a scattered, difficult-to-ac...

متن کامل

Supporting Evolution: Using Rationale in Use Case Driven Software Development

The requirements specification–as outcome of the requirements engineering process–falls short of capturing other useful information generated during this process, such as the justification for selected requirements, trade-offs made by stakeholders, and alternative requirements that were discarded. In the context of evolving systems and distributed development, this information is essential. Rat...

متن کامل

Feature-Based Rationale Management System for Supporting Software Architecture Adaptation

Each software architecture design is the result of a broad set of design decisions and their justi ̄cations, that is, the design rationale. Capturing the design rationale is important for a variety of reasons such as enhancing communication, reuse and maintenance. Unfortunately, it appears that there is still a lack of appropriate methods and tools for e®ectively capturing and managing the archi...

متن کامل

Capturing Evidence and Rationales with Requirements Engineering and Argumentation-Based Techniques

User Requirements Notation (URN) is a modeling language with two complementary notations for capturing goals and non-functional requirements as well as low level processes and functional requirements. URN helps documenting the rationale behind the decisions, however, it lacks gathering the evidences for these rationales and documenting stakeholder discussions. In this paper, we propose a framew...

متن کامل

ذخیره در منابع من


  با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید

برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید

ثبت نام

اگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید

عنوان ژورنال:

دوره   شماره 

صفحات  -

تاریخ انتشار 1993